While the binding extender is a generic coordination component without specific knowledge about possible types of bindings, the binding provider is a component that is specific to certain technology and defines binding types tailored to that technology.

A binding provider has the ability to create one or more types of bindings, as necessary for the technology it covers. Binding providers exist in form of binder components; the binder is a binding provider (can create new bindings) with certain additional capabilities, such as event linking, and ability to perform operations on bindings.

Each binding provider needs to register itself with the binding extender; this is done by properly setting the BindingExtender property of the binder. When you place the binder component from the Toolbox Items to your form’s or window's component tray, this setting is already made for you.

The most commonly used binder component is the PointBinder, which is described further below in a separate chapter. The PointBinder provides a unified approach to live binding; it merges the commonalities between OPC “Classic” and OPC Unified Architecture bindings into a single component.

Note: Earlier, OPC Data Client had used separate DABinder (for OPC Data Access) UABinder (for OPC Unified Architecture) component. They are now obsolete.